This page lists all plug-ins that have special changes to improve support for
this plug-in and all plug-ins for which this plug-in has special changes to
improve support. (At least, all plug-ins that I'm aware off and I didn't forget).
This plug-in provides an action bar API that my plug-in will use if
it is available. If you install it alongside my plug-in, the wand
cooldown/charges and custom tool durability will be shown in the
action bars of players.
It is possible to equip custom items from this plug-in on mobs from
Mythic Mobs. To do so, you need to configure a mythic mobs item in
a configuration file for mythic mobs (for instance ExampleItems.yml).
In such a file, you should define a custom item like this:
In the example above, item_name should be the Name that
you gave the custom item in the Editor. Not the Display name.
Then, you should configure a custom mob to equip this item in a mob file
(for instance ExampleMobs.yml):
The enchantments from the Crazy Enchantments plug-in can be used as the
default enchantments
of custom items. The crazy enchantments will be listed after the vanilla enchantments and have a
"[CRAZY]" suffix after their name. Furthermore, this plug-in has nice support for the Hellforge
enchantment on custom items. If a custom item would be repaired with the HellForged enchantment, its
custom durability will be repaired instead of the vanilla durability.
If crazy enchantments is not installed, nothing will happen, except a
message in the console stating that crazy enchantments doesn't seem to be installed.
Custom items and custom blocks can be used in Skripts.
Conditions
- %block% is [a] kci block
-
%block% is [a] kci %string%
Checks whether %block% is a kci custom block named %string%
- %block% (isn't|is not) [a] kci block
- %block% (isn't|is not) [a] kci %string%
- %itemstack% is [a] kci item
-
%itemstack% is [a] kci %string%
Checks whether %itemstack% is a kci custom item named %string%
- %itemstack% (is not|isn't) [a] kci item
- %itemstack% (is not|isn't) [a] kci %string%
Effects
-
give [a] kci %string% to %player%
Gives the custom item with name %string% to %player%
- give %integer% kci %string% to %player%
- give [a] kci %string% to %inventory%
- give %integer% kci %string% to %inventory%
-
place kci %string% at %block%
Places the kci custom block named %string% at the location of %block%
-
put [a] kci %string% in %slot%
Puts the custom item named %string% in slot %slot%
- put %integer% kci %string% in %slot%
-
%player% opens kci %string% at %string%
Lets %player% open the custom container named %string% at string host %string%
-
destroy kci %string% at %string%
Destroys the custom container named %strsing% at string host %string%
- destroy kci %string% at %string% and drop its items at %location%
- kci remove %integer% %string% from %inventory%
- drop [a] kci %string% at %location%
- drop %integer% kci %string% at %location%
- %entity% launches kci %string%
Expressions
- kci name of %block%
- kci name of %itemstack%
-
count of kci %string% in %inventory%
Counts how many times the kci custom item named %string% occurs in %inventory%
Examples
Custom items and custom blocks can be used in Denizen scripts. Unfortunately, the Denizen VS Code extensions
doesn't recognize them, so you will get some warnings and errors, which you should ignore.
Tags
- ItemTag.is_kci_item: returns true if and only if the item is a custom item from this plug-in
- ItemTag.kci_item_name: returns the name of the custom item, or null if the item is not a custom item
- LocationTag.is_kci_block: returns true if and only if there is a custom block at the location
-
LocationTag.kci_block_name: returns the name of the custom block at the location,
or null if there is no custom block at the location
-
InventoryTag.kci_count[custom_item_name]: counts the number of occurrences of the custom item with the
given name in the inventory. If the inventory has 1 stack of 4 custom items and 2 stacks of 3 custom items,
this would return 10
- <kci_items[custom_item_name]>: creates and returns a custom item (stack) from the custom item with the given name
- <kci_items[custom_item_name*amount]>: creates a custom item stack of amount custom items with the given name
Commands
- kci place [block_name:<string>] (at destination:<location>)
- kci_container [player_name:<player>] opens [container_name:<string>] at [host_string:<string>]
- kci_container destroy [container_name:<string>] at [host_string:<string>] (and drop items at [drop_location:<location>])
- kci_give ([amount:<int>]) [item_name:<string>] to [player:<player>]
- kci_give ([amount:<int>]) [item_name:<string>] to [inventory:<inventory>]
- kci_remove [amount:<int>] [item_name:<string>] from [player:<player>]|[inventory:<inventory>]
- kci_drop ([amount:<int>]) [item_name:<string>] at [location:<location>]
- kci_launch [projectile_name:<string>] from [shooter:<entity>]
Examples
This plug-in has small changes that allow users to use custom items from this plug-in in
its configuration files. For information of how to use this, take a look at
commoncore config info
at the section 'Custom Item and Textures (experimental)'.
Mimic is a plug-in that makes it easier to integrate custom item plug-ins with plug-ins that would like to use
custom items (and some other integrations that are irrelevant for this plug-in). Custom items from this plug-in
can be used by plug-ins that use Mimic. The identifiers of items from this plug-in will be like knokkoscustomitems:item_name
where item_name is the name you used in the Editor.
Just like Mimic, ItemBridge is a plug-in that makes it easier to integrate custom item plug-ins with plug-ins that would
like to use custom items. (This plug-in integrates with both Mimic and ItemBridge for optimal reach.) The identifiers of
items from this plug-in will be like KnokkosCustomItems:item_name where item_name is the name you used in
the Editor.